Drop HttpChainDescriptor pipeline-introspection fields; bump JasperFx 2.8.0 + Marten 9.4.0 (#3008)#3011
Merged
Conversation
… 2.8.0 + Marten 9.4.0 (GH-3008) Producer side of the JasperFx descriptor cleanup (#411). That removal of HttpChainDescriptor.Middleware / ServiceDependencies / Postprocessors (plus MiddlewareStepDescriptor) only shipped in JasperFx 2.8.0, so this is a coordinated critter-stack bump: - JasperFx family 2.4.1 -> 2.8.0 (RuntimeCompiler stays on 5.x) - Marten family 9.2.0 -> 9.4.0 (its JasperFx floor moved to 2.5.0; keeps the runtime gap to 2.8.0 small) - Weasel.* 9.0.1 -> 9.0.2 (required by Marten 9.4.0) - Polecat stays 4.2.1 (floor 2.2.0, satisfied by 2.8.0) In HttpGraphUsageSource: stop populating the three descriptor fields and delete the now-dead describeFrames / readServiceDependencies helpers (and the now-unused buildChainDescriptor services parameter). The CritterWatch Pipeline tab moves to the existing RequestHandlerSourceCode lazy fetch, which returns the actual compiled pipeline — no operator-facing information lost. Validated: full wolverine.slnx Release build clean (net9.0 + net10.0); CoreTests 1735, MartenTests 461, Wolverine.Http.Tests 777, PolecatTests 216 — all green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This was referenced Jun 3, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #3008. Producer side of the JasperFx descriptor cleanup (#411).
Status check first
Nothing for #3008 had landed on
main(the population code + helpers were intact, JasperFx still 2.4.1). #411 is now closed/shipped — but the property removal only exists in JasperFx 2.8.0, so the issue is still open and was newly unblocked, not closeable. The prescribed "bump JasperFx" therefore became a 2.4.1 → 2.8.0 jump coupled to the Marten family.Coordinated dependency bump
HttpChainDescriptor.Middleware/ServiceDependencies/Postprocessors(andMiddlewareStepDescriptor) are removed only in JasperFx 2.8.0 (still present in 2.5.0 / 2.6.x). So:Code change
In
HttpGraphUsageSource: stop populating the three fields and delete the now-deaddescribeFrames/readServiceDependencieshelpers (plus the now-unusedbuildChainDescriptorservicesparameter and theJasperFx.CodeGeneration.Framesusing). Per the issue, the CritterWatch Pipeline tab moves to the existingRequestHandlerSourceCodelazy fetch, which returns the actual compiled pipeline — no operator-facing information is lost.CascadingMessageTypes(added in 2.8.0) is unaffected.Validation
wolverine.slnxRelease build clean (net9.0 + net10.0), 0 warnings / 0 errors — i.e. no test references the removed JasperFx members.Notes
HttpGraphUsageSource, and the descriptor fields are gone from the type, so there's nothing to assert-negative on the producer side.🤖 Generated with Claude Code